feat: use X-Forwarded-Proto/Host for generated urls behind a reverse proxy - #181
Merged
Merged
Conversation
…proxy Co-Authored-By: Claude Fable 5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated URLs (channels.m3u entries, the xmltv link, and multi-variant playlist URIs) now use
X-Forwarded-Proto/X-Forwarded-Hostwhen present, so they work behind a TLS-terminating reverse proxy; without those headers, behavior is unchanged. Resolves theTODO: need scheme, host from reverse proxyinget_scheme_host.I'm new to Rust and collaborating with Claude Code on this PR. Most of the testing and verification was done by the AI, so extra scrutiny in review is welcome.